High availability cluster management

One important consideration for organizations is regarding the selection of the tool that administrators use to perform system maintenance, which involves how to quiesce or gracefully shutdown Pega 7 Platform servers. Available options for this process are detailed as follows:

• Incorporate Autonomic Event Services (AES) or to integrate this function into network operation centers.
  • AES provides access to high availability cluster management, in addition to a number of other features.
  • It is recommended that customers deploy AES to manage production systems with multiple clusters.
• Access MBeans in the System Management Administrator (SMA) directly or use the Pega 7 Platform's built in landing pages.
  • Organizations with sophisticated processes and hosting environments can choose to integrate high availability MBeans directly into a custom Pega 7 Platform management console.
  • SMA can be used directly from every Pega 7 Platform server in the system.
• Use high availability landing pages if an organization is not managing multiple clusters.
  • Architecturally, Pega 7 Platform servers are not allowed to know about each other. This constraint requires that the Pega 7 Platform cluster management pages use the system pulse to communicate (note that data is accurate after two pulse cycles). This introduces latency in the update of the Pega 7 Platform server run state that might not be optimal for large organizations.

To watch an educational video about quiesce and crash recovery, see the PegaTube video Webinar: PRPC High Availability on the PDN.

Related information

Open topic with navigation